Automate draft release #1623
Automate draft release #1623
Conversation
nhooyr
force-pushed
the
automate-release
branch
5 times, most recently
from
ebc9778 to
98a168d
Compare
| 1. Run `yarn release:github-draft` to create a GitHub draft release from the template with | ||
| the updated version. | ||
| 1. Summarize the major changes in the release notes and link to the relevant issues. | ||
| 1. Wait for the artifacts in step 2 to build |
There was a problem hiding this comment.
Should we number these incrementally instead of just with 1? Normally I don't pay much attention but since we called out step 2 I was trying to count up in my head and got lost a couple times lol especially since Github is rendering a gap after 2 for some reason and I kept thinking it was a separate paragraph. I always read the readmes raw so maybe that's just a me problem.
There was a problem hiding this comment.
Usually in markdown you don't want to number them to avoid forgetting updates since when it renders it's immediately there but I agree it is nice when looking at the raw markdown.
There was a problem hiding this comment.
Also I see no gap after 2, that's weird.
There was a problem hiding this comment.
It must have something to do with the specific screen size I have my browser at. My editor automatically updates the numbers so I was hoping there was something similar for yours.
There was a problem hiding this comment.
Goland aint as cool as emacs :(
| --draft "${assets[@]}" "v$(pkg_json_version)" << EOF | ||
| v$(pkg_json_version) | ||
|
|
||
| VS Code v$(vscode_version) |
No description provided.